Autonexus

1.0.x
(0 reviews)

ANX Integration

Purpose
The purpose of this document is to provide high level architecture followed in proof of concept in AutoNexus integration.

Scope
There are two workflows. One is to process the data from various brands such BP, PE,etc to AutoNexus SAP.
Another workflow is, to re-process the required data on the AutoNexus portal. Registered users can login into this portal and reprocess the data when required.

Architecture
Data Process

1. Data will be picked up from the respective brand for every 5 minutes (configurable) and send to Inchcape SFTP location and archive the in the source FTP location.
2. File will be splitted to individual records after the file read from the Inchcape SFTP location.
3. During this process, file will be named in the below format and saved in the Inchcape SFTP location:

                      <Brand Name>-<FileName>-<OrderNumber>.json
  1. JSON file will be processed to SAP and also archived in Inchcape SFTP location.

Data Reprocess

Portal
There are 2 registered users – Admin and non-admin. The below login screen will appear on

Home page will be displayed as below:


Post login of the user on portal, admin pages and user pages will be displayed as below:

Admin user page:


Admin can register user on click of the register link as shown in the above figure:

Admin can register another admin or non admin, on click of register button.

 

Non-Admin user page:


Post entering the file name in the above screen, on submit, reprocess API will be called to process the data which is explained in the respective section.
Reprocess Data
Pre Conditions

    Mule has received notification request to notify the end user.

Post Conditions

    Email notification will be sent to user’s email inbox.

Process Flow

post:/process:apiConfig
  1. Get the data from Endpoint.

2.

Notification

Pre Conditions

    Mule has received notification request to notify the end user.

Post Conditions

    Email notification will be sent to user’s email inbox.

Process Flow

post:/notification/email:apiConfig

  1. Get the data from Endpoint.

  2. Email send to the user.

  3. Upon exception, appropriate exception is captured and logged.

Reviews